The JavaBeans^TM Bridge for ActiveX

Goals for Release 1.0 of the JavaBeans Bridge for ActiveX

The main goal for Release 1.0 of the JavaBeans bridge for ActiveX is to provide users of legacy OLE/COM/ActiveX containers such as Word or Visual Basic with the ability to embed and use portable JavaBeans components in the same way they would previously embed and use platform-specific OLE/COM/ActiveX components.

This means that component developers can safely construct and deploy advanced, platform-independent JavaBeans components with the knowledge that they will also be fully usable inside of legacy applications.

See new features and changes in Beta 5 of the JavaBeans Bridge for ActiveX.

What's in the JavaBeans Bridge for ActiveX?

• A GUI packager utility that creates OLE type library information and win32 registry information for a selected JavaBean. This allows OLE/COM containers to correctly analyze and present a Bean. So for example, a Bean's properties will be correctly presented in a Visual Basic property sheet.

• Beans can fire events that can be caught by OLE/COM/ActiveX containers. This allows, for example, a Bean to fire an event that is caught by a Visual Basic script.

• Beans can act as servers for OLE/COM/ActiveX method invocation. This means that tools such as Visual Basic can invoke methods on Beans.

These technologies support the standard requirements for ActiveX components running inside of containers such as Internet Explorer, Word, or Visual Basic.

Please note that there are repaint glitches in Visual Basic while running certain Beans in Design Mode. Use Visual Basic "Run Mode" to get an actual view of your JavaBeans.

Upcoming Features

• Additional packaging support will be added so that developers can deliver beans that will be automatically installed in a target Win32 system during setup.

• Conversion support for .gif icons to Win32 icon format, for automatic conversion.

Beyond Release 1.0

The JavaBeans bridge for ActiveX Release 1.0 provides all the features required by typical ActiveX components.

However, JavaSoft will continue to work with the developer community to identify any additional features that are required for supporting Beans inside OLE/COM/ActiveX containers.

For example, typical ActiveX components act as sources for OLE/COM events and as servers for OLE/COM method calls, since it is the containers which typically catch events, and it is scripts which typically invoke methods. However, under some circumstances it may be useful for Beans to be able to directly invoke OLE/COM methods or to directly catch OLE/COM events (though the latter in particular seems very unlikely). However, if wider support for either catching events or firing method invocations should become necessary, JavaSoft will add this in future versions of the bridge.

Back to JavaBeans Home.